Network Supervisor's Toolkit/Network Supervisor's Toolkit.iso/novell/pb310a/problems.386

Text File | 1996-07-10 | 107.5 KB | 2,215 lines

COMMON PROBLEMS/SOLUTIONS/ANOMALIES/PATCHES FOR NETWARE 386 v3.10A

Last Update: January 4, 1991

     These are some of the common patches, problems, questions, and issues
     with Netware 386 v3.10a.  This list is not intended to be all-
     inclusive.  If more detail is needed on these issues, or on other
     issues not identified in this file, refer to the Novell Technical
     Information Database or contact your NetWare service provider.

***************************************************************************
                                DISCLAIMER

     The following are NOT official Novell statements, but rather
     troubleshooting ideas to help the customer resolve problems that may
     occur with NetWare 386 v3.10 rev. A.  These issues may change from
     week to week.  Be sure that you have the latest problems/solutions
     file from NetWire before drawing your conclusions.

***************************************************************************

This document is broken into the following issues:

     MEMORY ISSUES                                          pages 1-2
     ABENDS AND NLM PATCHES                                 pages 2-7
     DISK DRIVERS                                           pages 7-10
     SYSTEM MESSAGES                                        pages 10-12
     SHELLS                                                 pages 12-14
     LAN DRIVERS AND WORK STATION ISSUES                    pages 14-17
     UPGRADE ISSUES                                         pages 17-19
     UTILITIES                                              pages 19-22
     MISC FYIS and OTHER INFORMATION                        pages 22-24
     PRINTING                                               pages 24-33
     LISTING OF FILES, DATES and SIZES shipped with 3.10a   pages 34-42


MEMORY ISSUES:

PROBLEM 1:     Not enough memory to run NetWare 386 v3.10a.  The memory
               formula in the v3.10a manuals is incorrect.

SOLUTION:      Use the following rough formula as a guideline to calculate
               memory needs for a basic NetWare 386 v3.10a system:

               .023 * total drive size in MB / block size + 4 MB of memory

               Example: .023 * 600 MB drive / 4 k block size + 4 MB of
               memory = 7.45 MB of memory.

               If you have Macintosh name space added to the volume the
               formula is:

               .032 * total drive size in MB / block size + 4 MB of memory

               From a memory standpoint, you are better off creating a
               small volume for your Macintosh files and adding Macintosh
               name space to that volume only.


PROBLEM 2:     Common question:  "I know I'm tight on memory; what can I do
               in the meantime until my extra 4 MB comes in next week?"

SOLUTION:      a.   PURGE /ALL from the root directory to clean off deleted
                    files.
               b.   Do not load NLMs that are not needed.
               c.   SET IMMEDIATE PURGE OF DELETED FILES=ON (although you
                    will lose salvage capability the OS will not have to
                    keep track of deleted files).
               d.   Remove DOS (see page 251 of the system administration
                    manual).
               e.   Do not mount volumes that are not required.

PROBLEM 3:     The Register Memory command table on page 250 of the NetWare
               386 v3.10a System Administration manual (585/Rev 1.01) is
               incorrect.  The register memory command is only for machines
               with more than 16 MB of memory.

SOLUTION:      The table should read as follows:

               Total Memory        Start (hex)         Length(hex)

               20M                  1000000               400000
               24M                  1000000               800000
               28M                  1000000               C00000
               32M                  1000000              1000000
               36M                  1000000              1400000
               40M                  1000000              1800000

     NOTE:     Above 16 MB of memory is only supported in EISA machines
               with NetWare 386 v3.10a or PS/2 Model 90 and 95s.  If you
               are using more than 16 MB of memory, do not use 8-bit or 16-
               bit boards in the file server if the board uses bus
               mastering or DMA.  You will also be able to go above 16 MB
               of memory in a Model 90 or 95 (see register memory above) if
               the disk and LAN solution are both 32-bit.  It MAY also be
               possible to go above 16 MB of memory with a Model 80;
               however, it is not supported.


ABENDS AND NLM PATCHES:

               NetWare 386 v3.10a has patches that are loaded dynamically.
               Always make sure you are using the latest PATCHMAN.NLM when
               you are adding a new patch.  The latest will be in the
               latest upload.  Do not bother adding patches unless you are
               experiencing or anticipate experiencing the abend.  Keep all
               of the patches around so that if one of the following abends
               occur, you are able to add the patch quickly.

PROBLEM 1:     The message ABEND: "DeleteFileCompletely found an invalid
               TNode" would appear whenever a customer attempted to delete
               a file which had more than seven trustees assigned to it
               with Immediate Purge on.

SOLUTION:      DELFIX.ZIP

PROBLEM 2:     The message ABEND: "DeleteDirectory found invalid phantom
               list" would appear whenever a customer attempted to delete a
               directory which had more than eight trustees assigned to it.

SOLUTION:      DLDRFX.ZIP

PROBLEM 3:     ABEND: "Erase file should have done something".

SOLUTION:      ERASFX.ZIP.  This file contains ERASEFIX, a dynamic patch
               that is loaded at the file server console as a NetWare
               Loadable Module (NLM).  Do not load ERASEFIX unless you get
               the above abend.  It is not recommended.  ERASEFIX has been
               removed from NetWire.

PROBLEM 4:     ABEND: "MoveDeleteFiles found an Invalid DeleteFile list".
               This can occur with the first version ERASFX.ZIP
               (ERASEFIX.NLM).  It can be duplicated without any of the
               other patches applied.

SOLUTION:      Get ERASFX.ZIP dated after November 25, 1990 on NetWire
               which is the newest ERASEFIX.NLM.  We still strongly
               recommend not loading ERASEFIX.NLM.  ERASEFIX has been
               removed from NetWire.


PROBLEM 5:     With the first ERASEFIX.NLM applied, SALVAGE will not work
               properly.  If you delete a file in a given directory, you
               can not salvage the file back to the same name.

SOLUTION:      Under investigation.  Because of this and other problems.
               ERASEFIX.NLM has been removed from NetWire.  Do not load
               ERASEFIX.NLM.

PROBLEM 6:     ABEND: "Abend: Total sprintf string length was too long
               (Error code 00000000)".  This patch also fixes a problem
               that displayed invalid characters or user names when
               WATCHDOG cleared a connection.

SOLUTION:      WDOGFX.ZIP.
PROBLEM 7:     When bringing up the file server "Novell In-House Version"
               is displayed from the console sign-on screen of shipping
               versions of NetWare 386 v3.10 Rev. A.  This is only
               cosmetic.

SOLUTION:      NAMEFX.ZIP or NAMEFIX is a patch utility that removes the
               erroneous message.

PROBLEM 8:     The API function call ScanBinderyObject fails to properly
               recognize "?" as a wild card.  The failure was related to
               the size of the bindery name being searched for and the
               number of "?" wild characters (if greater than 12) entered
               in the search string.

SOLUTION:      SCBFIX.ZIP

PROBLEM 9:     NetWare 386 v3.10a has a caching problem.  Under heavy usage
               when data is read immediately after it is written to cache,
               the data read could result in the return of erroneous data.
               If cached data is read and rewritten to cache, the
               corruption would be saved to disk.  If the data is not
               changed in cache, the data will be saved correctly.  This
               problem exists primarily with random access applications
               (for example, database servers).

SOLUTION:      CACHFX.ZIP contains CACHEFIX.NLM.  All v3.10a file servers
               should have this patch loaded.

PROBLEM 10:    After an ABEND during the dump of diagnostics to diskette,
               the operating system could only dump the first 16 MB from
               memory.

SOLUTION:      Contact Novell Technical Support for a possible field test
               solution.  The solution has not been tested, but it is
               available through Tech Support if they determine there is a
               need.

PROBLEM 11:    NetWare would not allow files that were flagged RO to be
               opened with RW rights when the read only compatibility mode
               was set to ON.  The application returns messages such as
               "Access Denied" or "File Not Found".

SOLUTION:      FXOPEN.ZIP

PROBLEM 12:    A bug in NetWare 386 v3.10a will not allow a file's
               date/time to be set to 0.  Some applications known to set
               the date/time to 0 are Borland's Turbo C++ and Turbo Pascal
               products.  The compiler's "Build All" option within the
               integrated environment sets the date/time to 00's in order
               to force a full recompile of all source files.  Without this
               patch installed, the file's date/time remained unchanged.

SOLUTION:      DTTMFIX.ZIP

PROBLEM 13:    ABEND: "Bad resource tag detected in AES process".

SOLUTION:      Contact Novell Tech support for field test patch.  It is a
               static patch (RTAGFIX.EXE).  Do not run multiple static
               patches on the same file server.

PROBLEM 14:    ABEND: "PurgeTrustee found an entry it couldn't deal with".
                              If a workstation has requested a file to be
                              created, the request is put to sleep prior to
                              creating the file, and PurgeTrustee is
                              scanning the volume at this time, this ABEND
                              will occur.

SOLUTION:      PTFIX.NLM is available as a Field Test from Tech Support.

PROBLEM 15:    ABEND: "Clear Phantom called without primary directory
               number".

SOLUTION:      DELDIR.ZIP.

PROBLEM 16:    ABEND: "Invalid connection number or type passed to
               ReturnAConnectionNumber".

SOLUTION:      MONITR.ZIP

PROBLEM 17:    Synchronizing the system time on the file server.  Many
               customers have complained about their file server losing
               time.  In some cases, it loses only minutes or seconds.
               But, there have also been reports of losing hours each day.

SOLUTION:      NetWare sets the system clock initially when booting up.
               From then on it keeps the time using a software clocking
               algorithm.  When the file server switches into real mode, it
               stops keeping time and depends on DOS to keep the system
               time.  After switching back to protected mode instead of
               updating the time, the OS just continues where it left off.
               This could explain why the system time may be off by such
               varying amounts because the way NetWare clocks the time and
               the way DOS does it is not the same.  There is an NLM for
               NetWare 386 v3.1 that is available as a field test file.
               The file name is SYNC.ZIP.  Call Novell Technical Support to
               obtain this file.

PROBLEM 18:    There is a problem where the file server may hang when
               clearing connections in MONITOR.  There is also a problem
               where resources may not be released when exiting MONITOR.

SOLUTION:      MONITR.ZIP contains a new MONITOR.NLM.

PROBLEM 19:    If copying a file from a Macintosh workstation volume to a
               NetWare 386 file server volume, the creation date and time
               stamp are intact, but the modification date and time stamp
               are set to the date and time when the transfer was
               completed.

SOLUTION:      DTTMFIX.NLM (rev B)

PROBLEM 20:    "IPX received incomplete packet from <#node>" at the
               console.

SOLUTION:      IPXINC.ZIP.  This patch will quell the error message that is
               reported to the screen and the error log of the file server.
               It is to be used in conjunction with OEM and third party
               drivers until the drivers are fixed.  The offending driver
               can be in any client, bridge, or file server.  Old Client
               NE/2 and old Host NE2000 drivers are known to cause this
               problem and should be updated to currently released drivers.

PROBLEM 21:    The following messages:
               "Loader can not find public symbol"
               "MPCheckStringPatch"
               "Load file referenced undefined public variable"
               "Module Cachefix not loaded"

SOLUTION:      If you try to load a patch with an older PATCHMAN, the above
               messages occur.  The latest released PATCHMAN must be loaded
               in order to have all the latest patches recognized.  Make
               sure you are running with the latest dated PATCHMAN if you
               have loaded multiple patches.  When the PATCHMAN was rev'ed
               in October, all the NetWare 386 v3.10a patches were rev'ed
               as well.  The associated .ZIP files on NetWire were updated
               with the new PATCHMAN and patches (all dated 10-29-90).

PROBLEM 22:    ABEND: "TTSAbortTransaction detected a bad TTS file"

SOLUTION:      Contact Novell Tech Support for a field test solution.  It
               has been seen to be associated with BSPXCOM.NLM (Btrieve
               NLM).

PROBLEM 23:    Error "You have Exceeded Your outstanding NCP Search Limit"

SOLUTION a:    NCPLIM.ZIP.  NCPLIMIT provides for better management of file
               searches done on a NetWare 386 v3.10a file server.  This
               patch adjusts to applications written using the findfirst
               function.  If the findfirst search function is not completed
               correctly, NetWare 386 will generate the warning message
               "You exceeded your outstanding NCP directory search limit".
               If loading this NLM does not eliminate the warning message,
               the application will need to be rewritten according to the
               recommendations described in NCPLIMIT.DOC.

SOLUTION b:    This error has been documented earlier and has also been
               fixed by simply increasing the Maximum Outstanding NCP
               Searches = XXX (Pg 323 NetWare 386 v3.1 System
               Administration.  Range = 10 to 1000  Default = 51).  The
               question was, How will this increase affect my system?  The
               formula to calculate RAM usage is:

               24,000 X (Max ONCP Searches/1000) X Number of Workstations.

               The following files have been uploaded to NetWire and should
               be merged into Library 16 by the end of the day:

PROBLEM 24:    Error when loading an NLM.  "Loader cannot find public
               symbol"

SOLUTION:      This is an indication that you are loading a v3.0 NLM.
               Double check the date and size of the file.

PROBLEM 25:    Abend: "General Protection Processor Exception"

SOLUTION:      a.   It is most often caused by hardware problems in the
                    file server (memory, system board, cards, etc), or out
                    on the LAN.
               b.   It can also be caused by power surges.  Make sure the
                    UPS can handle the dips and spikes in power.
               c.   A good place to start if you have this abend is to load
                    the MONITOR.NLM and look in LAN information under
                    general and custom statistics.  If you see any errors
                    climbing under LAN information, it is a good indication
                    of potential LAN hardware problems (NIC cards,
                    terminators, cables, hubs, maus, cables not to spec,
                    etc).  The general statistics are documented in the
                    System Administration manual in the monitor section.
                    The custom statistics are documented in Appendix A of
                    the System Administration manual.  If you have a driver
                    from a third-party vendor, obtain the custom statistics
                    documentation from them.
               d.   This has also been seen in heavy I/O through a third-
                    party driver specifically written for a 16-bit card
                    when the card was only an 8-bit card.  Investigate your
                    LAN drivers and cards.

DISK DRIVERS:

PROBLEM 1:     We are seeing FAT errors on boot up right after installing
               NetWare 386 v3.10a with the PS2SCSI.DSK driver.  However,
               mounting the volume from the console (outside of the
               AUTOEXEC.NCF) has no problem.  Many PS2SCSI.DSK
               installations will never experience the problem.

SOLUTION:      This appears to be associated with older revisions of the
               SCSI controller.  We have tested it in our Technical Support
               labs with both caching and noncaching controllers and have
               not experienced any problems.  If you should happen to run
               across this, you will have to boot up manually until you can
               get a different controller.  The newest PS2386.ZIP also must
               be used if these and other problems are being experienced.

PROBLEM 2:     PS2SCSI.DSK shipped with v3.10 was reporting a
               Non-Media-Error when the SCSI device returned a completion
               of 07 - Adapter Hardware Failure and 0ch - Command Completed
               with failure.  This would result in deactivation of the SCSI
               device.

SOLUTION:      PS2386.ZIP.  This version of the driver will retry when
               encountering the 0ch error rather than deactivating the
               device.

PROBLEM 3:     We need more detail on SCSI adapters in the PS/2s.  We may
               have an older revision because we are still having trouble
               with our drive and we've already tried the patched
               PS2SCSI.DSK in PS2836.ZIP.

SOLUTION:      Engineering Change Announcement ECA032 goes into more detail
               on these hardware changes.

               SCSI Adapter        Old P/N        -    New P/N
                                   -------------       ------------
               Without cache       FRU P/N15F6561     FRU P/N 85F0002
                                   Option 6451005     Option 6451109

               The following systems above the referenced serial number
               have the up-level adapter and are not affected.  This change
               is necessary for systems below this serial number range.

               8580-121 9000000           8565-061 4011000
               8580-321 9200000           8565-121 4512000
               8580-A21 7600000
               8580-A31 2600000

PROBLEM 4:     Are IBM SCSI drivers available for IBM PS/2 Models 90 and
               95?

SOLUTION:      The PS2SCSI.DSK that ships with NetWare 386 v3.10a supports
               models 90 and 95.

PROBLEM 5:     We have seen several problems on IBM machines with SCSI
               controllers and non-IBM drives.

SOLUTION:      Most problems have work-arounds; for example, there are
               patches from IBM and Novell for drive access problems with
               Seagate drives in PS/2s.  Oftentimes, the manufacturer of
               the drive is aware of issues needed to make their drive
               work.

               For example, some problems exist with the Model 80-A31 with
               a SCSI caching controller and Core drives.  You can load the
               needed files for v3.1 off of the floppy drive but not off of
               a DOS partition on the hard drive.  It would return errors
               like "C not ready" or "error reading load file".  SCSI has a
               numbering scheme for devices attached to a SCSI controller,
               0-7 with 7 being the highest priority.  The IBM SCSI
               controller comes set at priority 7, the highest priority.
               Since the controller takes a device number itself when
               trying to load or read data from the SCSI chain, the
               controller looks for the next device in line, in this case
               device 6.

               Core International ships its SCSI drives jumpered to SCSI
               device 0.  Thus, if you attach this device 0 with a DOS
               partition to the IBM SCSI controller which is set to 7, you
               will get errors concerning drive C.  The Core drive can be
               set to SCSI device 6 with a DOS partition to work with the
               Model 80 A31 and the PS2SCSI.DSK driver for NetWare 386
               v3.1.

               NOTE: This has been tried with another third party drive and
               after downing the file server, COMMAND.COM cannot be found.
               So this may not be an issue with the drive you are dealing
               with.

PROBLEM 6:     Problems with loading ISADISK driver v3.10 (shipped with
               NetWare 386 v3.10a) more than once MAY be resolved by using
               the NetWare 386 v3.0 ISADISK driver.

SOLUTION:      ISA30.ZIP

PROBLEM 7:     Do IDE drives work with NetWare 386 v3.10a with ISADISK?

SOLUTION:      Some do.  Contact the manufacturer of the drive to see if
               they have tested the drive with v3.10a.  The drive
               manufacturers interpret the IDE specifications differently.
               Some drives cannot use user-definable options and run with
               ISADISK.

PROBLEM 8:     Have any problems been reported having one volume span
               multiple drives?

RESPONSE:      Most of the problems that we have experienced have been
               associated with using a noncertified driver/drive and/or
               controller.  The controller having been tested with a given
               disk driver is important.  Following these basic guidelines
               solves most problems associated with spanning drives.
               However, keep in mind with spanning drives -- if one drive
               fails the entire volume is lost, even if other segments of
               the volume reside on the good drives.

PROBLEM 9:     DCB.DSK.  NetWare users who are upgrading to NetWare 386
               v3.10 may need to upgrade their Novell DCBs.

SOLUTION:      NetWare users who are upgrading to 386 v3.10 may need to
               upgrade their Novell Disk Coprocessor Boards (DCB).

               NetWare 386 v3.10 was written to support the latest in
               hardware technology.  This includes DCBs with revision E or
               higher of the DCB firmware.  DCBs with firmware revision D
               or earlier will not work with NetWare 386 v3.10.  Under
               NetWare 386 v3.10, the hard drives will not be visible to
               the system when using these older revisions.  This will
               generally affect 50-pin DCBs that are a few years old.

               The revision of the DCB firmware is identified at location
               817-186 at the bottom left of the board; the firmware
               revision will not necessarily correspond to the DCB board
               revision number.  Location 817-186 will contain a 28-pin
               chip identified by part number 817-186-001.  The revision
               level will follow the part number (i.e. 817-186-001E or
               817-186-001 rev E).  If the revision level is D or earlier,
               an upgrade is necessary.

               An upgrade to a DCB with the latest firmware revision is
               available through Federal Technologies RMA Department at
               (800)-366-4526.

PROBLEM 10:    Adding a DOS Formatted Drive to a DCB with Adaptec 4070
               (possibly 4000 also).  After replacing a drive with a DOS
               formatted drive and booting NetWare 386, the INSTALL utility
               will not see the replacement drive.  This was tested in the
               lab with two mirrored Rodime 204E drives (also tested two
               Maxtor 1140's).

SOLUTION:      In order for INSTALL to see the drive, the drives must be
               unmirrored.  Load DISKSET and select low-level format from
               the drive configuration window.  Another window appears with
               the title "Selected Disk Specifications".  At this point
               press Insert and it will automatically start formatting the
               drive without any warning.  (This is an undocumented
               feature).  The last thing you must do after the format is
               finished is to save the DCB configuration.  Even though the
               configuration is already there, you must save it again or
               INSTALL will still be unable to see the drive.

PROBLEM 11:    When loading the DCB NLM the error "Hardware Initialization
               Failure" is returned.  This is seen specifically on some
               Compaq machines.

SOLUTION:      These machines come with a mouse port that is enabled with a
               jumper on the motherboard.  The port conflicts with IRQ 12
               that is used by a Novell channel 2 DCB, and possibly other
               hardware cards.  Check your Compaq documentation and move
               the jumper to disable the mouse port. (Note:  you cannot
               just remove the jumper completely.)  Also keep in mind that
               many drives have parity jumpers on the back of the drive
               that must be disabled for the drive to be recognized.

PROBLEM 12:    Our file server appears to be running fine.  However, after
               downing the file server, we have to run VREPAIR every time
               we want to mount our volumes.  What is wrong?

SOLUTION:      Often times this has ended up being associated with the
               controller not working correctly.  If you are experiencing
               this problem, try switching to a later revision of the same
               controller.  If you are still having problems, change to a
               different brand or make of controller.

SYSTEM MESSAGES:

PROBLEM 1:     Interrupt controller detected a Lost or Spurious hardware
               interrupt.  This has been seen on some faster machines.

SOLUTION:      These are not fatal messages; they are passed through from
               the hardware.  Your system should function normally.  Some
               machines have PAL chips or hardware modifications to help
               keep interrupts from being lost.  To suppress these
               messages, enter at the console:

               SET DISPLAY LOST INTERRUPT ALERTS=OFF
               SET DISPLAY SPURIOUS INTERRUPT ALERTS=OFF

               See the Systems Administration manual.

PROBLEM 2:     The following or similar errors occur along with the
               inability to perform a task at either the file server or
               workstation:

                    Out of dynamic work space.
                    The cache memory allocator exceeded minimum cache
                    buffer left limit.
                    Semi-permanent memory allocator is out of memory xx
                    semi-permanent allocation request failed.

RESPONSE:      This is most often caused by not having enough memory on the
               file server.  See the Memory section of this same document
               to determine what is needed and workarounds.

PROBLEM 3:     "Process Did Not Relinquish Control Frequently" error
               message at the file server.

SOLUTION:      More than likely you will not need to worry about this
               error.  It was originally designed to detect processes that
               were taking too much of the file server's processing time
               but apparently doesn't function the way it was designed.
               However, it could be indicative of a problem with an NLM
               taking too much processing time.

PROBLEM 4:     Message at file server "Hot fix did not need to be
               redirected".

RESPONSE:      You should only be concerned with this message if it occurs
               on a regular basis.  If a block, for whatever reason,
               couldn't be written to, this message will occur if the
               operating system was finally successful in writing to the
               block.  In other words the operating system isn't going to
               give up after the first try.  At the same time it is
               alerting you that the "Hot Fix did not need to be
               redirected".  Watch your Hot Fix errors in Monitor.  If Hot
               Fix is filling up your drive, it may be in need of
               replacement.

PROBLEM 5:     Error:  (Found in error log) Locus = 8  Class = 0  Code = 0
               Severity = 4 Account XXXXX deleted by user NOT-LOGGED-IN on
               station XX 1 active connection terminated.

RESPONSE:      Cause:  A supervisor equivalent deletes a user and then
               immediately logs out before the routine gets serviced.  When
               the routine finally gets serviced by the file server, the
               connection status is NOT-LOGGED-IN.  There is no security
               threat with this message and should not be cause for alarm.


NOTE:          The July 1990 issue of NetWare Application Notes contains
               additional Disk, Memory, and Accounting messages.
               The October 1990 issue contains system messages: Bindery,
               Internal processes, Abends, Packet Services and Queue
               Management.  To order, call [phone].

SHELLS

PROBLEM 1:     We have had different application problems reported by
               different revisions of the shell.

SOLUTION:      If you are having problems, be sure to try at least the 3.01
               rev. B, 3.01 rev. D, and 3.01 rev. E shell to verify that
               what you are experiencing is a shell issue.

History for the NetWare DOS Shell v3.01

               The following is a history of the major changes that have
               occurred in the NetWare DOS shell v3.01 and higher.  This
               document is updated with each additional release of the
               NetWare DOS shell.

               NETX.COM            3.01 Rev. A              5-8-90
               XMSNETX.EXE         3.01 Rev. A              5-8-90
               EMSNETX.EXE         3.01 Rev. A              5-8-90

          o    Loading SiteLock by Briteworks would fail, causing the
               DOS workstation to hang.  This problem was corrected with
               the 3.01 rev. B shell.

               NETX.COM            3.01 Rev. B              6-6-90
               XMSNETX.EXE         3.01 Rev. B              6-6-90
               EMSNETX.EXE         3.01 Rev. B              6-6-90

          o    Using the Preferred Server option caused the network
               response time to be functionally slower than if the user did
               not use this option.  The 3.01 rev. C shell corrected this
               problem.

          o    When using DOS 4.0 with EMSNETx and XMSNETx shells, the DOS
               directories would not display correctly under Windows.  This
               was corrected with the 3.01 rev. C shell.

          o    The enhanced memory shells were not sending header
               information when using job configurations that included
               escape codes.  For example, a job that should print
               landscape would print using the default mode (portrait).

          o    When printing to a captured LPT device an error message
               "Device not ready" would appear.  A retry would allow the
               job to continue.  The 3.01 rev. C shell corrected this
               problem.

          o    Fake roots were being deleted on paths with volume names
               before the path was determined valid.  ie. CD PRN: would
               delete the fake root.  This was fixed with the 3.01 rev. C
               shell.

          o    On 286-based file servers, the Dynamic Memory Pool (DMP) 1
               was not being released properly with the XMSNETx and EMSNETx
               shells causing the server to hang eventually.  With the 3.01
               rev. C shell, the memory is released when exiting the
               Windows DOS Prompt.

               NETX.COM            3.01 Rev. C              * Not released
               XMSNETX.EXE         3.01 Rev. C              * Not released
               EMSNETX.EXE         3.01 Rev. C              * Not released

               * The NetWare DOS Shells rev. C was made available to
               NetWare Developers only.  The NetWare DOS shells v3.01 rev.
               D was released to all users and contains all the 3.01 rev. C
               changes.

               NETX.COM            3.01 Rev. D              9-7-90
               XMSNETX.EXE         3.01 Rev. D              9-7-90
               EMSNETX.EXE         3.01 Rev. D              9-7-90

          o    When running the 3.01 rev. D shell on a NetWare v2.15 or
               less operating system, external program execution (using the
               #) from the login script does not work unless the user has
               open privileges at the volume root.  This has been corrected
               in the shells dated 9/18/90 or later.

          o    NVER will return Rev. C instead of Rev. D.  This has been
               corrected in the shells dated 9/18/90 or later.

               NETX.COM            3.01 Rev. D              9-18-90
               XMSNETX.EXE         3.01 Rev. D              9-18-90
               EMSNETX.EXE         3.01 Rev. D              9-18-90

          o    When using the DOS 4.0 "TrueName" (undocumented DOS command)
               command invalid data was returned to the shell.  This
               invalid data causes Emerald's System's backup to not
               function properly.  The 3.01 rev. E shell corrects this
               problem.

          o    Microsoft Link was reporting a scratched file error when
               linking a large number of files.  This was corrected in 3.01
               rev. E of the NetWare DOS shell.

          o    Added support for VERSION.EXE utility.  This support was not
               present in earlier releases of the shell.

          o    Corrected a problem with the rename function where the wrong
               error code would be returned to applications such as
               Platinum Accounting by Advanced Business Microsystems.  This
               error was also exhibited with the NETGEN message:

               Cannot find DRVRDATA.DAT.

          o    Corrected a problem where the shell was not correctly
               maintaining the default file server after logout when an
               X.25 bridge is used.

          o    On ELS NetWare file servers, you would get one less
               connection than the maximum when using remote boot.  The
               3.01 rev. E shell corrected this problem allowing the user
               to get all connections to the file server.

          o    Enabled file caching in EMSNETx and XMSNETx shells.  File
               caching was not enabled in earlier releases of the enhanced
               memory shells.  It also fixed a problem where these shells
               were passing an incorrect file server address to IPX.  The
               error most commonly seen was "No response from server
               <servername>"

          o    Added the /? option to the command line which displays
               version and usage information.

          o    Added a feature in the 3.01 rev. E shell that tells the user
               that a TSR is loaded when trying to unload the shell.

               NETX.COM            3.01 Rev. E              11-27-90
               XMSNETX.EXE         3.01 Rev. E              11-27-90
               EMSNETX.EXE         3.01 Rev. E              11-27-90

LAN DRIVERS AND WORKSTATION ISSUES:

PROBLEM 1:     The TRXNET.LAN Arcnet driver that shipped with NetWare 386
               v3.10a has exhibited a problem with receive buffers reaching
               the maximum.  This may result in the network or workstation
               "leg" hanging following the logout of one or more
               workstations.

SOLUTION:      Use TRXNET.ZIP.  CAUTION:  This version of the TRXNET file
               server driver should be considered a beta version.  Only use
               it with 8-bit cards.  If you must use a 16-bit card, the
               RXNET.LAN for v3.0 dated 8-24-89 (RXNET.ZIP on NetWire) is
               relatively stable and can be used on a v3.10a file server
               (however the driver was only designed for 8-bit cards).
               Keep in mind that most Arcnet cards have drivers that are
               specifically written for the card.

PROBLEM 2:     Workstation gets a "Connection No Longer Valid, Abort Retry"
               error at the workstation when doing an SLIST, USERLIST, or
               any other command that scrolls information on the screen.

SOLUTION:      This is caused by an I/O address 2EOh conflict in the
               workstation.  This is most often seen when the workstation
               is using the RXNET default I/O of 2EOh.  The Microsoft
               library call used by the SLIST and other commands to find
               the number of lines accessible on the monitor uses I/O
               address 2EOh, which has known problems.  The solution is to
               choose an I/O option other than 2EOh for RXNET.

PROBLEM 3:     RXNET.LAN 3.0 driver dated 8-24-89 and ARCMON.EXE (Arcnet
               Monitor Utility). ABEND: General Protection Interrupt.
               We have verified that v2.17 of ARCMON.EXE by Brightworks
               will cause the NetWare 386 file server to ABEND with a GPI
               (v2.17 was the one tested, other versions of ARCMON may act
               in the same manner).

SOLUTION:      TRXNET.LAN, available on NetWire for v3.10a, should not have
               this problem.

PROBLEM 4:     TOKEN.LAN file server driver getting "Error Receiving or
               sending on Network abort retry".

SOLUTION a:    This has been seen with 16/4 cards only.  If a 16/4 card is
               in the file server when copying large files from the
               workstation, insert the following in the STARTUP.NCF file to
               increase the packet size to approximately 4 KB:

               SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=4202

SOLUTION b:    If this does not correct the problem, delete the line from
               the STARTUP.NCF file and use the following in the
               AUTOEXEC.BAT file with IPX v3.01 rev. B:

               IPX O,TBZ=2048

               This reduces the packet size from the default 4 KB to 2 KB
               and has been known to solve the problem.

SOLUTION c:    The TBZ parameter can also be used at the file server and
               can also solve the problem (Load TOKEN.LAN TBZ=xxxx).

PROBLEM 5:     Where are the latest Token-Ring drivers including source
               routing?

SOLUTION:      TRN050.ZIP.

PROBLEM 6:     Our LANSUP conflicts with IBMs NetBIOS.

SOLUTION:      LANSUP.ZIP (TRN050.ZIP also contains the Latest LANSUP).

PROBLEM 7:     The two main problems the new field test drivers address is
               support for the PS/2 Model 55LS and the capability to boot a
               diskless workstation across an IBM bridge.  Until now this
               capability did not exist.  Although, you can boot across a
               Novell bridge (with the RPL VAP loaded at the bridge).

SOLUTION:      Contact Novell Tech Support for a field test solution.

PROBLEM 8:     "Error Frame Type Already Loaded, Attempt To Reinitialize
               Reentrant Module Failed" loading TOKEN.LAN twice with two
               16/4 cards in the NetWare 386 v3.10a file server.  Type
               "Load Token Slot=1 Name=Accounting" and it loads fine.  Type
               "Load Token Slot=2 Name=Backbone" for second card and the
               error occurs.

SOLUTION:      By typing "Load Token Port=A24 Name=Backbone" for the second
               card, it will work fine.  A24 is the secondary Token-Ring
               card.  The primary card would be "Port=A20".

PROBLEM 10:    The Compaq 286n diskless workstation won't remote boot using
               the CPQTOKNW.LAN driver.

SOLUTION:      The current version of CPQTOKNW.LAN (as of November 1990)
               does not support remote boot.

PROBLEM 11:    Cannot login using a 3C507 adapter in the workstation and a
               NetWare 386 v3.10a file server.

SOLUTION:      A file server driver for NetWare 386 is available from 3Com.
               However, there is no NetWare 386 workstation driver for the
               3C507.  The NetWare 286 workstation driver provided by 3Com
               is not compatible with v3.10.

PROBLEM 12:    Problems have been seen when loading and binding a LAN
               driver more than once in the AUTOEXEC.NCF file.  You will
               sometimes be prompted for the driver parameters when binding
               the driver to the second card.

SOLUTION:      Place brackets around the driver parameters in the bind
               statement.  See System Administration Manual page 176 and
               177.  example:

               LOAD NE2000 int=3 port=300 frame=ethernet_II
               BIND IPX to NE2000 [int=3 port=300 frame=ethernet_II]
               net=xx.

PROBLEM 13:    Packet receive buffers are reaching maximum with any LAN
               drivers.

SOLUTION:      See Systems Administration Manual page 293 to increase
               minimum and maximum packet receive buffers if necessary (for
               example, sometimes multiple interface cards in the file
               server require increasing the minimum and maximum).

               Keep in mind that it is possible for the drivers themselves
               to cause receive buffers to max out (for example, the
               TRXNET.LAN shipped with v3.10a had this problem).  However,
               it is most commonly related to hardware (i.e. card, cable,
               hub, terminator etc).  For example, in one case associated
               with packet receive buffers maxing out, 93 ohm terminators
               rather than 50 ohm terminators were used in combination with
               a flaky NE2000 card in the file server.

PROBLEM 14:    When using remote reset on slow diskless workstations with a
               high-speed (33 MHz) file server using NE2000.LAN, the
               workstation will only boot one time out of every ten.  This
               is the same problem that we have seen before with fast file
               servers and fast interface cards with slow XTs and 3C501
               cards.  Basically, The workstation makes a request to the
               file server.  The file server is so fast that it responds
               before the workstation at the other end is ready for a
               response.

SOLUTION:      If you want to keep the slow workstations, you can put a
               bridge between the file server and the workstations.  Having
               to pass through the bridge may lengthen the time it takes
               for the file server to respond.  The workstations with
               remote boot may be able to attach and login.

               If you have many 3C501s with remote reset problems, put the
               3C501s in the faster machines and put NE1000s and other
               cards in the slower XTs until you can replace the older
               machines.

PROBLEM 15:    Our interface card vendor claims Novell has not released the
               v3.1 Driver Specifications so they cannot make their driver
               fully compatible with NetWare 386 v3.10a.

SOLUTION:      Novell provided preliminary specifications for vendors in
               the second quarter of 1990.  Vendors with questions on LAN
               driver specifications should contact the Independent
               Manufacturer Support Program at Corporate Headquarters.  The
               assembler for v3.1 is the same as v3.0.

UPGRADE ISSUES:

PROBLEM 1:     The upgrade process asks for all of the SYSTEM and PUBLIC
               diskettes, but not all files are copied.

SOLUTION:      This has been seen on machines not certified for NetWare
               386.  Often times the solution comes from the hardware
               vendor in either a patch or a newer BIOS.  As a quick
               workaround after running the upgrade, manually copy all of
               the files from the SYSTEM and PUBLIC directories on the
               diskettes to the SYSTEM and PUBLIC directories respectively
               on the file server.

PROBLEM 2:     The most common problem that causes UPGRADE not to correctly
               bring across information associated with the binderies, user
               info, etc. is that BINDFIX.EXE was not run before the
               UPGRADE.

SOLUTION:      Please run BINDFIX on the v2.x file server before running
               UPGRADE, as requested in the Install manual.

PROBLEM 3:     UPGRADE was running fine until it hit a file and couldn't
               copy it.  We had to delete the file and rerun UPGRADE.  Why?

SOLUTION:      Running VREPAIR on the source file server before doing the
               upgrade may help with these types of problems.  Another
               workaround is to use NCOPY and XCOPY to copy the remaining
               subdirectories and files that weren't copied.  UPGRADE
               requires the source to be correct.  This problem is being
               looked into.

PROBLEM 4:     The passwords were lost after upgrading from NetWare v2.1x
               to v3.10a.

SOLUTION:      The password encryption scheme was changed from v2.1x to
               v3.10a.  This is mentioned in the Installation manual in the
               "follow up after upgrade section".

PROBLEM 5:     Upgrading from NetWare 286 v2.15 to 386 v3.10a may result in
               error messages saying that no files were transferred because
               they were in use.  This could happen on every file on the
               286 file server.

SOLUTION:      An older shell can cause this error.  Update the shell in
               the workstation.

PROBLEM 6:     How do we merge three 286 file servers onto one 386 file
               server?

SOLUTION:      Run UPGRADE individually on each 286 file server and it will
               merge the binderies onto the 386 file server and the trustee
               assignments will transfer across as well (along with the
               data).

PROBLEM 7:     UPGRADE.EXE Upgrading from NetWare 286 v2.15 to 386 v3.1
               using the UPGRADE method.  Passwords will not convert.

SOLUTION:      Since the encryption scheme changed in v3.1 from v2.15,
               passwords will not convert.  You must login as supervisor
               and enter a password or blanks in order for the user to set
               his own password.  As a side note:  if you are upgrading
               from v2.0a, the passwords will convert.

PROBLEM 8:     After doing an upgrade to NetWare 386 v3.10a, users attempt
               to login and receive the error "Unknown Error Returned By
               Attach (89Fb)".

RESPONSE:      This message will occur if the supervisor hasn't gone into
               SYSCON and given the users new passwords.  Passwords are not
               carried over in the upgrade process.

PROBLEM 9:     When a workstation logs in to a 386 file server on an
               internet, it gets an "Access Denied" error even though it is
               possible to login to a 286 file server.

SOLUTION:      The 386 LOGIN.EXE encrypts the password across the wire.
               You have attached to a 286 file server and are using that
               copy of LOGIN.EXE which does not encrypt the password like
               the 386 lOGIN.EXE does.  There is a default "Set" parameter
               on the file server expecting an encrypted password.  When it
               gets an unencrypted password, the file server returns the
               "Access Denied" error.  This "Set" parameter can be set to
               allow unencrypted passwords by typing at the file server
               command line:

               Set Allow Unencrypted Passwords = On

               This would also hold true for the ATTACH, MAP, or any other
               command or utility that attempts to attach you to a Netware
               386 file server from a 286 file server.

PROBLEM 10:    The 386 file server comes up, but when executing Net3 or
               Net4, the error "A File Server Could Not Be Found" is
               returned.

SOLUTION:      This error usually indicates a hardware problem with either
               a card, cable, or terminator.  Keep in mind however that
               NetWare 386 expects you to resolve any IRQ or I/O conflicts
               in the file server before you install the software; it does
               not resolve them during installation like NetWare 286's
               NETGEN.  Check your file server to ensure there are no
               conflicts with IRQs, I/O addresses, etc.

PROBLEM 11:    "No Free connection Slots" at the workstation.

SOLUTION:      Check the basics.  It is usually associated with cards,
               cables, terminators, drivers, addressing, etc.

UTILITIES:

PROBLEM:       The CAPTURE.EXE that shipped with NetWare 386 v3.10a in some
               cases may have problems associated with the banner,
               particularly if the wrong name is printed on the banner or
               the name is missing on the banner.

SOLUTION:      Use CAPTURE v1.21 on NetWire (CAP121.ZIP).


PROBLEM:       CASTOFF ALL has a problem when using time restrictions.  If
               the user has CASTOFF ALL in his login script and the user
               logs in with a time restriction, at the time expiration he
               should be logged off, but is not.  However, by using CASTOFF
               in the login script, everything works fine; the user will be
               logged out.

RESPONSE:      Do not use both CASTOFF ALL in login script and time
               restrictions.  For now if you need both you may have to
               execute CASTOFF ALL from a batch file.

PROBLEM:       FLAG.EXE does not allow flagging of a file as execute only.

RESPONSE:      The documentation has the feature documented but the
               FLAG.EXE code does not have the feature included.  If you
               need to flag files execute only, use FILER.

PROBLEM:       The !LOGOUT does not work with Novell's MENU.EXE v1.23 using
               MENUPARZ.EXE v1.23.

SOLUTION:      MENU.ZIP is a hybrid of MENU files.  It combines
               MENUPARZ.EXE v1.22 with MENU.EXE v1.23 to add !LOGOUT
               functionality.  MENU.ZIP has two Novell menu solutions in
               it; use the one that works best for you.

PROBLEM:       NBACKUP v1.1 does not restore disk space restrictions.

RESPONSE:      This is under investigation.

PROBLEM:       NDIR.EXE  The error "divide overflow" is displayed at the
               workstation as the directory is being sorted with NDIR.EXE
               on NetWare 386 v3.10a.

SOLUTION:      Use NDIR.ZIP on NetWire.

PROBLEM:       NETBIOS.EXE.  If you have any problems that you feel may be
               associated with NetBIOS, make sure you are running with the
               latest NETBIOS.EXE dated 11-15-90   3:48p.

SOLUTION:      NB301F.ZIP  (The readme explains some of the enhancements).

PROBLEM:       NPRINT will not work using the path with the filename.  Nor
               can you print a file on a drive that you are not currently
               mapped to.  The following error occurs:

               F:USERS\>NPRINT G:\MINE\FILE S=SERVER Q=HPLASER NT NB
               Queuing data to Server SERVER, Queue HPLASER.
               SYS:MINE\
               The file FILE not found.

SOLUTION:      a.   Define the path on the current drive to a directory
                    below your current directory position.

                    F:\USERS>NPRINT \USERS\OTHERS\FILE S=SERVER Q=HPLASER
                    NT NB Queuing data to Server SERVER, Queue HPLASER.
               OR
                    Where the file is on another mapped drive, do NOT
                    specify the entire path.  For example, your default
                    drive is F: and you want to print from drive M: where
                    M:=SERVER/SYS:USERS/JOHN.  You may issue the command:

                    NPRINT M:filename

               b.   The NPRINT.EXE form name parameter returns the
                    incorrect form number.  If you experience this or any
                    other problems with NPRINT.EXE, you may use the v2.15
                    or v3.0 NPRINT.EXE.

PROBLEM:       NPRINT.EXE.  When NPRINT in NetWare 386 v3.10a is used with
               the form name option, an incorrect form number is given to
               that print job.

RESPONSE:      This problem is being looked into.  For now, if a form name
               is needed as a parameter use, an older NPRINT.EXE.

PROBLEM:       PAUDIT.EXE  NetWare 386 v3.10a.  Using accounting to track
               service requests gives incorrect numbers when you logout and
               login again.

EXAMPLE:       Create a user and login to the system as usual (accounting
               enabled of course); then immediately log out.  Run PAUDIT
               and you might get:

               Charge: 12,  Requests: 1052, Blks Read: 353C4, Blks written:
               0, Connect time: 0

               Login again (same or different user) and immediately log
               out.  Run PAUDIT:

               Charge: 19, Requests: 2118, ....(All the rest is the same as
               the first time)

WORKAROUND:    Reboot the workstation after logging out.  The totals are
               not reset when a user logs out.  Only when NET? is issued do
               the service requests get reset to zero.  This means, of
               course, that if a user logs out and does not reboot the
               workstation, another user logging in will get charged for
               the last user's service requests used.  It is billing
               double, triple, etc. for the same SRs.

PROBLEM:       P_Station.  In the Installation manual appendix A, page 302,
               the syntax for P_Station is as follows: "If P_STATION =
               0000000001ab" then write "You need to ... etc."  The syntax
               as shown creates a login script error.  Script error: "could
               not interpret line".  The original line was: "if p_station =
               0000000001ab then write you need to ....etc."

SOLUTION:      The correct syntax is If P_station = "0000000001ab" then
               write "statement".

PROBLEM:       PURGE ALL fails after the entry limit is reached.

SOLUTION:      You must PURGE ALL several times in order to clear all of
               the deleted entries.

PROBLEM:       RCONSOLE.EXE.  The connection to the file server is lost if
               you press "No" when asked if you want to exit.

SOLUTION:      The work around for now is to reenter RCONSOLE to establish
               the connection.

PROBLEM:       RCONSOLE.EXE  How can we reboot the 386 file server using
               RCONSOLE?

RESPONSE:      Given that there is a valid AUTOEXEC.BAT file that runs
               SERVER.EXE and the AUTOEXEC.NCF loads all the appropriate
               NLMs, including the password for RCONSOLE, start RCONSOLE
               and execute the following commands:  REMOVE DOS, DOWN the
               file server, and then EXIT.  When the EXIT can't find a DOS
               environment, it will do a warm boot to the file server. You
               will have to reconnect to the file server after it reboots.

PROBLEM:       SMODE.EXE can not be used with file names greater that five
               characters.  For example, you can do SMODE on a file
               1234.EXE and it will work; however, if the file is
               123456.EXE, it will not work.

RESPONSE:      This is under investigation.

PROBLEM:       VREPAIR.NLM.  VREPAIR didn't finish.  Does that mean that
               we've lost all of our data after our file server crashed?

SOLUTION:      If you have multiple problems on your drive, you may have to
               run VREPAIR multiple times.  Do not give up after one or two
               times.  Depending on the damage and the size of the drives,
               seven or eight or more times may be necessary.   Customers
               have been able to mount their volumes successfully and
               continue running fine after a hard crash.  Remember, if you
               begin crashing frequently, you may want to backup more often
               if deemed necessary.


MISCELLANEOUS FYIs AND OTHER INFORMATION

PROBLEM 1:     NetWare 386 v3.1 users get the error message:  Drive Mapping
               Operation Could Not Be Completed "the mapping in system
               login script" error code 000a.  This error message comes up
               during the execution of the login script.

SOLUTION:      Increase environment space in the CONFIG.SYS file with:

               shell = COMMAND.COM  /p /e:xxxx.
               (where xxxx is the amount of environment space - try 1024).


PROBLEM 2:     NetWare 386 .NCF files are not fully explained in NetWare
               386 documentation.

EXPLANATION:   You may already be aware that NetWare 386 makes use of two
               files during startup:  STARTUP.NCF and AUTOEXEC.NCF.  These
               NCF files contain a list of commands to be executed by the
               console command interpreter.  NCF stands for NetWare Command
               File.  What is not obvious from the documentation is that it
               is possible to produce .NCF files for your own use which
               contain commonly used console commands.  These are ordinary
               ASCII files which can be created and placed in SYS:SYSTEM
               (or other search directory) and must have the NCF extension.
               To execute an .NCF file, simply type the name of the file -
               the Console command interpreter will do the rest...  Some
               examples are shown below :

               MONITOR.NCF - Used to load the monitor program
               ----------------------------------------------
               LOAD MONITOR

               BYE.NCF - Used to shut down and reboot the file server
               --------------------------------------------------
               REMOVE DOS
               DOWN
               EXIT

               STATUS.NCF - Display useful status information
               ----------------------------------------------
               CONFIG
               DISPLAY NETWORKS
               DISPLAY SERVERS

               BSTOP.NCF - Supplied with Btrieve for NetWare 386 to unload
               Btrieve NLMs
               --------------------------------------------------
               UNLOAD BSPXCOM
               UNLOAD BTRIEVE

               In addition to the standard Console commands, you may also
               use the following commands within an NCF file :

               ECHO ON   - Display commands as they are executed (for
                         debugging)

               ECHO OFF  - Switch off display of commands as they are
                         executed (default)

               REM          - Remark (not displayed on execution)
               ;            - Remark (not displayed on execution)
               #            - Remark (not displayed on execution)

PROBLEM 3:     Subject:  How is NetWare 386 "486 Aware"?

RESPONSE:      See September 1990 Application notes for more detail.
               NetWare 386 v3.00 and v3.10 do not do any kind of check to
               determine if the machine has a 80486 processor.  The same
               instruction paths are executed on both the 80386 and 80468
               processors.

               The 80486 processor has a more efficient pipeline than the
               80386 processor.  This allows it to execute most
               instructions in less clock cycles.  This pipeline can be
               further enhanced by not accessing the same CPU register two
               instructions in a row.  NetWare 386 is "486 aware" in the
               coding of the assembly instructions.  The assembly
               instructions have been arranged as much as possible to not
               use the same registers two instructions in a row.  This
               allows the CPU to typically execute these instructions in
               one clock cycle verses the two clock cycles that could be
               required if the instruction accessed a register that was
               modified in the previous instruction.

PROBLEM 4:     When you do a SLIST, all 386 file servers show a node
               address of 1.

RESPONSE:      This is normal for 386 file servers and the network address
               that is displayed is the new internal IPX address of the
               file server, not the cable address.  To get the common cable
               or network address, do a "CONFIG" at the file server or a
               "USERLIST" at the workstation.

PROBLEM 5:     Getting "Router Configuration" errors showing up on the
               internet or unable to see a particular file server.

SOLUTION:      Double check that the "IPX Internal Network Address" number,
               assigned to any 386 file server, does not conflict with any
               network or node addresses (including DOS Process numbers on
               nondedicated file servers) on the internet.  This number
               must be completely unique!

PROBLEM 6:     Does Novell have any information on viruses?

SOLUTION:      The July 1990 issue of Application Notes, part number
               164-000011-001, contains an article "An overview of Virus
               Prevention Strategies in a NetWare Environment".  Call
               801-429-7550 rather than ext. 7555 to order subscriptions or
               reprints of a particular issue.  There are many virus scan-
               type utilities out there.  Rather than endorse any
               particular product, a good place to look is in LAN Times, on
               Netwire, or call third party companies that have a history
               of writing products for Novell or network environments.

PROBLEM 7:     A tape backup with NetWare 386 v3.1, using a Gigatrend
               LANsafe system, would hang.

SOLUTION:      Increase the maximum outstanding NCP search limit to fix the
               problem.

PRINTING

PROBLEM 1:     The most common problems associated with printing in the
               past three to four months end up being associated with not
               having the latest printing utilities.  Make sure you have
               deleted and recreated your print servers and queues with the
               latest PCONSOLE.  What are the latest printing utilities?

SOLUTION:      The printing utilities shipped with NetWare 386 v3.1 are the
               latest.  If you upgraded from v3.0 or have used any of the
               older printing utilities, you will want to check the dates
               and sizes on the printing files.  Make sure you are at least
               using the following files:

               FILE                SIZE      DATE
               -------------------------------------------
               PSERVER.NLM         73641     6-11-90
               RPRINTER.HLP         1803     5-29-90
               RPRINTER.EXE         6326     6-11-90
               RPRINT$$.EXE        76892     6-01-90
               PSERVER.EXE        108262     6-01-90
               PSC.EXE             20037     7-26-90
               PCONSOLE.EXE       213096     5-11-90
               PCONSOLE.HLP        33117     5-31-90
               PRINTDEF.EXE       180211     5-04-90
               PRINTDEF.HLP        36714     5-04-90
               PRINTCON.EXE       152661     5-21-90
               PRINTCON.HLP        12261     5-29-90

               The rest of the printing problems and solutions are based on
               the assumption that you do have the latest printing
               utilities.

PROBLEM 2:     Unloading PSERVER.NLM displays the "Module did not release
               #### resources from memory" message.

SOLUTION:      This message is only cosmetic.  PSERVER.NLM does not release
               the resources to the operating system (OS).  However, the OS
               will come along and pick them up anyway when needed.

PROBLEM 3:     When booting PSERVER.EXE displays not enough SPX
               connections.

SOLUTION:      Increase SPX connections to 60 in the SHELL.CFG (see NetWare
               386 v3.10a Installation Manual Appendix B, page 337).

PROBLEM 4:     RPRINTER.EXE will return an error 776 if the SPX connection
               is still there.  This error is returned when a printer
               connection is not free at the print server.  It could be
               because there are not enough printers defined in PCONSOLE or
               because the SPX connection has not yet timed out after a
               workstation with RPRINTER loaded was rebooted.  This has
               been seen with warm booting the PC running RPRINTER.

SOLUTION:      There is a recommended batch file for a workstation that
               loads RPRINTER.  The batch file should be:

                    1. Echo off
                    2. :loop
                    3. rprinter printserver printer#
                    4. if errorlevel 1 goto loop
                    5. Echo RPRINTER loaded Successfully!!!

               This batch file should help get rid of the 776 error.
               Placing a PAUSE in your AUTOEXEC.BAT file before loading IPX
               and NET3 may also help.

PROBLEM 5:     RPRINTER.EXE occasionally drops it's connection and the jobs
               stack up in the queue.

SOLUTION:      a.   Increase the SPX ABORT TIME OUT in the SHELL.CFG file
                    on the machine running RPRINTER.  Increase the SPX
                    ABORT TIMEOUT from the 30 second default (540 ticks) to
                    about 800 ticks.  To do this, create a SHELL.CFG file
                    and put "SPX ABORT TIMEOUT=800".  The 800 is arbitrary;
                    you may have to play with this value.  Place the file
                    in your boot drive (see Appendix B of the NetWare 386
                    Installation Manual for SHELL.CFG parameters).

               b.   Losing SPX connections with no communication for 30
                    seconds or more could be evidence of a bad board or
                    driver.  Make sure you are running the latest IPX and
                    the latest driver for the card.

PROBLEM 6:     RPRINTER and Windows 3.0 on the same workstation has trouble
               working together and sometimes locks up.

RESPONSE:      Running RPRINTER with Windows 3.0 is not yet supported.

PROBLEM 7:     RPRINTER or PSERVER hangs.

SOLUTION:      This may be a hardware limitation!  You can try the
               following suggestions:

               a.   Move the printer to a different workstation.
               b.   Swap interface cards and update the drivers.
               c.   If you are using an add-on parallel/serial port card,
                    swap it out or use another brand of port card.
               d.   Delete the print server queues and printer definitions
                    and then recreate them.
               e.   Check PSERVER and RPRINTER files for the latest
                    version.  If you are using what was shipped with
                    NetWare 386 v3.10a, you do have the latest versions.
                    The latest versions are available on NetWire or from
                    your NetWare service provider.
               f.   Remove any device that is between the workstation and
                    printer and retry.
               g.   Switch to another printer port.

PROBLEM 8:     Problems getting RPRINTER to work.

SOLUTION:      a.   Interrupt settings selected in PCONSOLE printer
                    configuration do not match interrupt settings on
                    workstation port.
               b.   There is an interrupt conflict between other ports or
                    devices within the workstation.
               c.   Because ROM BIOS does NOT use interrupts, the
                    workstation or port card may not support interrupts.
               d.   The port is not fully functional, meaning that the port
                    can receive a character, but cannot issue an interrupt
                    to signal NetWare to send the next character.
               e.   Another solution may be your setup in PCONSOLE.  With
                    PCONSOLE v1.32 that ships with NetWare 386 v3.10a when
                    defining printer port interrupts, PCONSOLE accepts your
                    changes to interrupts and sets them correctly, but
                    after exiting and then coming back to the printer
                    configuration screen, the interrupt settings will
                    appear not to have changed.  In reality they have
                    internally changed, but a PCONSOLE bug does not show
                    this change to the screen.  Instead it shows you the
                    defaults.

PROBLEM 9:     The PCONSOLE printer configuration screen allows the user to
               select polled (no interrupts) for remote printers.  Upon
               returning to the printer configuration screen, the printer
               shows that it has been changed back to using interrupts.

RESPONSE:      RPRINTER functionality is currently only designed to work
               with interrupts.

PROBLEM 10:    Printing is slow.

SOLUTION:      Some computer ports are not capable of being driven by
               interrupts because the COM ports have been set up to work
               only with DOS which polls the ports. If you are experiencing
               slow printing problems such as one character every 3
               seconds, a line of print every 4-6 minutes, or a page of
               print every hour or so, this could be your problem.  DOS
               uses the ROM BIOS to access the printer port, whereas
               NetWare outputs directly to the port.  When using NetWare
               and interrupts, NetWare sends the character to the port and
               then waits 3 seconds for an interrupt.  If one does not
               occur, NetWare scans the port.  If all is well, it sends
               another character.  Thus, the appearance of slow printing.
               Change to polled mode on the printer port and see if the
               printer speed increases.  The port could also be partially
               working with it being able to receive a character, but not
               being able to send an interrupt acknowledgement.  This would
               cause slow printing.

PROBLEM 11:    HP Laser series 3D printers running as local printers in the
               polled mode (no interrupts) have experienced problems with
               printing garbage characters.

SOLUTION:      Switching to interrupt driven and increasing the buffer in
               the printer configuration seems to help the problem.

PROBLEM 12:    Lose characters or graphics coming out with garbage.

SOLUTION:      In addition to the all of the above recommendations, put a
               NT (no tabs) parameter in your capture statement.  This most
               commonly fixes graphics with garbage.  Increase the timeout
               (TI) in the capture statement if your document gets cut off
               before being completed.   Losing characters has also been
               associated with the need to increase the buffers for the
               printer in PCONSOLE under printer configuration from the
               default of 3 to a value between 10 and 20.

PROBLEM 13:    The CAPTURE.EXE shipped with NetWare 386 v3.10a in some
               cases may have problems associated with the banner,
               particularly if the wrong name is printed on the banner or
               the name is missing on the banner.

SOLUTION:      Use CAPTURE v1.21 on NetWire (CAP121.ZIP).

PROBLEM 14:    We print landscaped and condensed.  The next guy comes along
               and the printer does not reset back to normal printing.  We
               know that we're not losing our minds and we're aware of the
               problem with the old PRINTDEF.EXE.  What else is wrong?

SOLUTION:      The 3.01 rev B shells that ships with NetWare 386 v3.10a are
               the problem.  Get the latest shells off of NetWire version
               3.01 rev D or better DSWIND.ZIP - 3.01 rev D shells.
               SH301E.ZIP - 3.01 rev E shells.

PROBLEM 15:    PSERVER.EXE, NLM, and JOB OWNER problems.  The JOB OWNER
               will not be notified when entered on either the permanent or
               temporary notify list.

SOLUTION:      It is being looked into.

PROBLEM 16:    PCONSOLE Notify Groups is not working properly.  There is a
               permanent and temporary notify list.  Specifying groups in
               the notify list does not work properly.  If a group is
               specified (either by itself or in a list containing users
               and groups) in the permanent list, nobody gets notified when
               the printer needs attention.  If only users are specified,
               then a user will be notified.  In the temporary list if only
               a group is listed in the notify list, then nobody will get
               notified.  If users and groups are listed then the
               appropriate user will get notified.

SOLUTION:      It is being looked into.

PROBLEM 17:    What do the error codes associated with printing mean?

RESPONSE:      These printing error codes can be found in the developers
               manuals and can be helpful in solving printing related
               problems.

ERROR CODES:   64   0x0040    PSC_NO_AVAILABLE_SPX_CONNECTIONS:
                    The shell has not been configured to get enough SPX
                    connections.  This can be remedied by changing the
                    SHELL.CFG file.

               65   0x0041    PSC_SPX_NOT_INITIALIZED:
                    The SPX shell has not been loaded.

               66   0x0042    PSC_NO_SUCH_PRINT_SERVER:
                    The client has attempted to attach to a print server
                    that is not advertising and hence not running.

               67   0x0043    PSC_UNABLE_TO_GET_SERVER_ADDRESS:
                    The network address of the advertising print server is
                    not in the bindery.

               68   0x0044    PSC_UNABLE_TO_CONNECT_TO_SERVER:
                    The client cannot attach to the print server for some
                    reason that cannot be identified.

               69   0x0045    PSC_NO_AVAILABLE_IPX_SOCKETS:
                    All available IPX sockets are already in use.

               70   0x0046   PSC_ALREADY_ATTACH_TO_A_PRINT_SERVER:
                    The NetWare Print Server C library only allows a client
                    to be attached to one print server at a time.  Clients
                    may write their own libraries if they wish to attach to
                    more than one print server at a time.

               71   0x0047    PSC_IPX_NOT_INITIALIZED:
                    The IPX shell has not been loaded.

               237  0x00ED    PSC_CONNECTION_TERMINATED:
                    This message can be returned on any call.  The  SPX
                    connection has been broken or the connection between
                    the client and the print server has been broken.

               257  0x0101    PSE_TOO_MANY_FILE_SERVERS:
                    The print server is already attached to as many file
                    servers as is possible and cannot attach to any more.
                    The current version of the NLM print server can attach
                    to only one file server.  The dedicated workstation and
                    the VAP print servers can attach to up to eight file
                    servers.

               258  0x0102    PSE_UNKNOWN_FILE_SERVER:
                    The client has requested to attach to a file server
                    that is not known to the print server.
               259  0x0103    PSE_BINDERY_LOCKED:
                    The bindery of the specified file server is locked and
                    cannot be accessed at this time.  A bindery will be
                    locked if a supervisor is running BINDFIX or some other
                    application that monopolizes the bindery.

               260  0x0104    PSE_FILE_SERVER_MAXED_OUT:
                    The file server is already attached to as many
                    different connections as is possible and cannot attach
                    to any more.  File servers using NetWare 386 v3.0 can
                    handle up to up to 250 connections.

               261  0x0105    PSE_NO_RESPONSE:
                    The specified file server is recognized by the print
                    server, but does not respond to the ATTACH call for
                    some reason.  This usually means that the file server
                    has just gone down.

               262  0x0106    PSE_ALREADY_ATTACHED:
                    The print server is already attached to the specified
                    file server.

               263  0x0107    PSE_CANT_ATTACH:
                    The print server cannot attach to the specified file
                    server for some reason that cannot be identified.

               264  0x0108    PSE_NO_ACCOUNT_BALANCE:
                    The file server is charging for services and the print
                    server does not have an account balance.  This error
                    will not occur unless accounting has been installed and
                    the print server has not been assigned an account
                    balance.

               265  0x0109    PSE_NO_CREDIT_LEFT:
                    The file server is charging for services and the print
                    server has exceeded its credit limit.  In this version
                    of the NetWare print server, print servers are
                    automatically given unlimited credit when an accounting
                    application is installed.  This error will not occur
                    unless the credit limit has been altered with a user
                    supplied application.

               266  0x010A    PSE_INTRUDER_DETECTION_LOCK:
                    The print server is locked out of the file server for a
                    certain amount of time because someone has tried to
                    login as the print server several times and has used
                    the wrong name or wrong password.  The number of
                    incorrect logins before lockout and the length of time
                    of the lockout is set up in the SYSCON utility.

               267  0x010B    PSE_TOO_MANY_CONNECTIONS:
                    A print server with the exact same name as the one
                    trying to login is already logged into the file server.


               268  0x010C    PSE_ACCOUNT_DISABLED:
                    This error will not occur unless a supervisor has
                    specifically altered the print server account so what
                    it is disabled.

               269  0x010D    PSE_UNAUTHORIZED_TIME:
                    The print server has attempted to login at a time that
                    has been designed by the supervisor as an unauthorized
                    time in the SYSCON utility.

               270  0x010E    PSE_UNAUTHORIZED_STATION:
                    The print server has attempted to login from a work
                    station that has not been authorized in the SYSCON
                    utility.  This will not occur unless it has been
                    specifically designed by the supervisor.

               271  0x010F    PSE_NO_MORE_GRACE:
                    The print server's password has expired and was not
                    changed in the amount of time allowed as a grace
                    period.

               272  0x0110    PSE_LOGIN_DISABLED:
                    All logins have been temporarily disabled by the
                    supervisor.

               273  0x0111    PSE_ILLEGAL_ACCT_NAME:
                    An account name using illegal characters (such as ?, *,
                    etc.) has been entered.

               274  0x0112    PSE_PASSWORD_HAS_EXPIRED:
                    This is a warning.  The password has expired and must
                    be changed in the amount of time designated as grace
                    time in the SYSCON utility.

               275  0x0113    PSE_ACCESS_DENIED:
                    An incorrect print server name or password was
                    entered.

               276  0x0114    PSE_CANT_LOGIN:
                    The print server cannot login to the specified file
                    server for some reason that cannot be identified.

               512  0x0200    PSE_NO_SUCH_OBJECT:
                    An object (such as a user, queue, or group) has been
                    requested that does not exist in the bindery of the
                    specified file server.

               513  0x0201    PSE_NOT_AUTHORIZED_FOR_QUEUE:
                    The print server is not in the list of authorized print
                    servers for the specified queue.

               514  0x0202    PSE_QUEUE_HALTED:
                    The queue operator has set a flag in the PCONSOLE
                    utility so that no more print servers can attach to
                    that queue.

               515  0x0203    PSE_UNABLE_TO_ATTACH_TO_QUEUE:
                    The print server is unable to attach to the specified
                    queue for some reason that cannot be identified.

               516  0x0204    PSE_TOO_MANY_QUEUE_SERVERS:
                    The specified queue is already attached to  the maximum
                    number of print servers it is allowed.

               768  0x0300    PSE_INVALID_REQUEST:
                    An SPX packet has been sent with a request code that is
                    not recognized by the print server.

               769  0x0301    PSE_NOT_ENOUGH_MEMORY:
                    The print server cannot allocate the amount of  memory
                    needed to meet the request.

               770  0x0302    PSE_NO_SUCH_PRINTER:
                    A request has been made for a printer that does not
                    exist.

               771  0x0303    PSE_INVALID_PARAMETER:
                    The request that was made is valid, but one of the
                    parameters contains a value that is not valid.

               772  0x0304    PSE_PRINTER_BUSY:
                    This message is returned if a Mark, Eject, or Change
                    Remote Printer PRIVATE/SHARED mode is sent while the
                    printer is printing.

               773  0x0305    PSE_PRINTER_NOT_CONNECTED:
                    The client has attempted to access a remote printer
                    that has not connected yet.

               774  0x0306    PSE_GOING_DOWN:
                    The DOWN command has been issued to the print server
                    and it is waiting for all of its printers to finish
                    printing their jobs before if shuts down.  However, the
                    printer that the client has tried to access.

               775  0x0307    PSE_CANT_DETACH_PRIMARY_SERVER:
                    The print server cannot detach from its primary file
                    server.

               776  0x0308    PSE_ALREADY_IN_USE:
                    The client has attempted to set up a remote printer
                    using a printer number that is already in use.

               778  0x030A    PSE_NOT_ATTACHED_TO_SERVER:
                    When attempting to add a queue or add an object to
                    notify, the client has specified a file server that is
                    not attached to the print server.

               779  0x030B    PSE_ALREADY_IN_LIST:
                    The client has attempted to add an object to a notify
                    list or add a queue to a queue service list that is
                    already in that list.

               780  0x030C    PSE_DOWN:
                    The print server is down and must be restarted.  This
                    message is returned only during the time interval
                    between when the DOWN command is issued and when the
                    print server is actually shut down.

               781  0x030D    PSE_NOT_IN_LIST:
                    The client has attempted to change or delete a print
                    queue that is not in the queue service list or an
                    object that is not in the notify object list.

               782  0x030E    PSE_NO_RIGHTS:
                    The client does not have the necessary user or operator
                    rights to perform the attempted function.

               1024 0x0400    PSE_UNABLE_TO_VERIFY_IDENTITY:
                    This message is returned if a login to print server is
                    sent with incorrect data in it.  The connection number
                    and file server name don't match the address that the
                    client is calling from.

               1025 0x0401    PSE_NOT_REMOTE_PRINTER:
                    The user has attempted to make a remote printer call to
                    a printer which is not a remote printer or set up a
                    remote printer using a print number which is not a
                    remote printer number.

LISTING OF FILES, DATES and SIZES shipped with v3.10a


     BACKUP       <DIR>      8-08-90  10:47a
     BRGEN-1      <DIR>      8-08-90  10:48a
     BTRIEVE      <DIR>      8-08-90  10:51a
     DOSUTIL- 1   <DIR>      8-08-90  10:53a
     DOSUTIL- 2   <DIR>      8-08-90  12:46p
     DOSUTIL- 3   <DIR>      8-08-90  12:46p
     HELP-1       <DIR>      8-08-90  12:54p
     HELP-2       <DIR>      8-08-90   1:00p
     PRINT        <DIR>      8-08-90   1:02p
     SHGEN-1      <DIR>      8-08-90   1:07p
     SYSTEM-  1   <DIR>      8-08-90   1:13p
     SYSTEM-  2   <DIR>      8-08-90   1:13p
     UPGRADE      <DIR>      8-08-90   1:30p



BACKUP/PUBLIC

    $RUN     OVL        2400   7-13-89   9:30 am
    IBM$RUN  OVL        2400   7-13-89   9:30 am
    SYS$ERR  DAT        6489   7-29-87   9:57 am
    SYS$MSG  DAT       22298  12-22-87   8:42 am
    SYS$HELP DAT       17343   8-11-87  10:06 am
    CMPQ$RUN OVL        2400   7-26-89  10:26 pm
    DIBI$DRV DAT          30   6-29-89   8:53 pm
    SELDIBI  HLP         229   6-24-89   3:45 pm
    NBACKUP  EXE      292762   5-31-90   3:12 pm
    NBACKUP  HLP       33253   5-29-90   2:10 pm
    NBACKUP  OVL      288700   5-31-90   3:13 pm
    WANGTEK  EXE       22950  12-08-89   3:19 pm
    SELDIBI  OVL       54250  12-08-89   3:18 pm
    NBACKUP  COM       10262  12-08-89   3:18 pm


BRGEN-1

    CMPQ$RUN OVL        2400   7-26-89  10:26 pm
    JUMPERS  HLP        1766   4-05-90   4:40 pm
    BROPTION DAT        1005   6-30-89   2:06 pm
    DCONFIG  EXE       22247   6-06-88  11:46 am
    BRGEN    EXE       27633   9-16-88  10:58 am
    SYS$HELP DAT       17343   8-11-87  10:06 am
    SYS$ERR  DAT        6489   7-29-87   9:57 am
    SYS$MSG  DAT       22298  12-22-87   8:42 am
    BRIDGE   DAT          36   6-30-89   2:06 pm
    CONSOLE  COM         103   8-25-87   7:57 am
    JUMPERS  EXE       76203   5-07-90   1:38 pm
    ECONFIG  EXE       24269   4-14-88   8:21 am
    VOLUMES  DAT          53   9-08-88   4:08 pm
    BCONFIG  EXE      173245   8-10-89   1:52 pm
    ROUTE    VP0        3832   4-18-90  10:35 am
    A3C503A1 OBJ        6381   4-13-90  10:59 am
    B3C503A1 OBJ        6381   4-13-90  11:00 am
    C3C503A1 OBJ        6381   4-13-90  11:00 am
    D3C503A1 OBJ        6381   4-13-90  11:00 am
    NLINK    EXE       37633   8-10-89   9:37 am
    BRIDGE   OBJ      129386   8-07-89   3:37 pm
    NDBRIDGE OBJ      156834   8-07-89   3:37 pm
    RPL      VP1        1806   5-08-90   4:29 pm
    $RUN     OVL        2400   7-13-89   9:30 am
    IBM$RUN  OVL        2400   7-13-89   9:30 am
    ANE200A1 OBJ        6041  11-29-89   1:36 pm
    BNE200A1 OBJ        6041  11-29-89   1:36 pm
    CNE200A1 OBJ        6041  11-29-89   1:36 pm
    DNE200A1 OBJ        6041  11-29-89   1:37 pm
    ANE2A1   OBJ        6478  11-29-89   2:04 pm
    BNE2A1   OBJ        6478  11-29-89   2:04 pm
    CNE2A1   OBJ        6478  11-29-89   2:04 pm
    DNE2A1   OBJ        6478  11-29-89   2:04 pm
    ANE1000  OBJ        4424  12-04-89   2:16 pm
    BNE1000  OBJ        4424  12-04-89   2:16 pm
    CNE1000  OBJ        4424  12-04-89   2:16 pm
    DNE1000  OBJ        4424  12-04-89   2:17 pm
    3C505A1  LAN         953   6-11-90   2:47 pm
    3C503A1  LAN         455   6-11-90   2:47 pm
    3C523A1  LAN        1320   6-11-90   2:47 pm
    NE1000   LAN         904   6-11-90   2:47 pm
    NE2A1    LAN        1777   6-11-90   2:47 pm
    NE200A1  LAN         923   6-11-90   2:47 pm
    TOKENA2  LAN         202   6-11-90   2:47 pm
    TRXNTA1  LAN         874   6-11-90   2:47 pm
    ATRXNTA1 OBJ        6699   6-11-90  12:05 pm
    BTRXNTA1 OBJ        6699   6-11-90  12:05 pm
    CTRXNTA1 OBJ        6699   6-11-90  12:05 pm
    DTRXNTA1 OBJ        6699   6-11-90  12:05 pm
    RPCONFIG COM        2726   6-08-90   5:15 pm
    SRCONFIG COM        3086   6-11-90   3:13 pm
    TRCONFIG COM        3402   6-08-90   4:55 pm
    SUBSYS   SYS        4271   5-30-89   2:14 pm
    NULLB    OBJ         377   5-13-87   9:59 am
    NULLC    OBJ         377   5-13-87   9:59 am
    NULLD    OBJ         377   5-13-87   9:59 am
    BTOKENA2 OBJ        4975   5-28-90   8:02 pm
    CTOKENA2 OBJ        4975   5-28-90   8:02 pm
    DTOKENA2 OBJ        4975   5-28-90   8:03 pm
    ATOKENA2 OBJ        4975   5-28-90   8:02 pm
    BCONFIG  HLP       29987   5-29-90   3:41 pm
    A3C523A1 OBJ        9113   6-02-90  11:29 am
    B3C523A1 OBJ        9113   6-02-90  11:29 am
    C3C523A1 OBJ        9113   6-02-90  11:30 am
    D3C523A1 OBJ        9113   6-02-90  11:30 am
    B3C505A1 OBJ        9640   8-03-89   3:11 pm
    D3C505A1 OBJ        9640   8-03-89   3:12 pm
    A3C505A1 OBJ        9640   8-03-89   3:10 pm
    C3C505A1 OBJ        9640   8-03-89   3:11 pm


BTRIEVE

    README   DOC        7570   6-01-90   9:40 am


BTRIEVE/PUBLIC

    BCONSOLE EXE       48462  12-11-89   3:54 pm
    BCONSOLE HLP        1923   9-01-89  10:32 am
    BREQUEST EXE       17874   3-22-90   3:46 pm
    BROLLFP  EXE       19020   3-10-90   8:04 pm
    BROLLFWD EXE       47869  12-11-89   3:49 pm
    BTRCALLS DLL       24762   3-22-90   3:58 pm
    MAKLOCAL EXE       11008   3-11-90   7:22 pm
    WBROLL   EXE       20688   3-15-90  11:24 pm
    WBTRCALL EXE       27628   3-22-90   3:51 pm



BTRIEVE/SYSTEM

    BCONNLM  HLP        1583   9-13-89   8:28 am
    BCONSOLE NLM       44669   5-23-90   2:03 pm
    BROUTER  NLM       16443   5-30-90  10:42 am
    BSETUP   HLP        3926  10-13-89   4:40 pm
    BSETUP   NCF          58   9-11-89   2:30 pm
    BSETUP   NLM       46282   5-02-90  10:02 am
    BSPXCOM  NLM       12498   5-30-90   9:21 am
    BSPXSTUB NLM        1170   5-23-90   3:46 pm
    BSTART   NCF         127   5-31-90  10:26 am
    BSTOP    NCF          33   8-25-89  10:51 am
    BTRIEVE  NLM       57560   6-06-90   8:45 am

DOSUTIL-.1/PUBLIC

    FLAGDIR  EXE       27093   3-23-90  11:06 am
    GRANT    EXE       33369   3-27-90   4:04 pm
    CASTOFF  EXE       12633   7-20-89   2:11 pm
    CASTON   EXE        8209   7-18-89  11:14 am
    CHKDIR   EXE       18053   7-18-89  11:15 am
    VERSION  EXE       21551   3-28-90  10:09 am
    $RUN     OVL        2400   7-13-89   9:30 am
    IBM$RUN  OVL        2400   7-13-89   9:30 am
    USERLIST EXE       25413   7-18-89  12:00 pm
    CMPQ$RUN OVL        2400   7-26-89  10:26 pm
    SYS$MSG  DAT       22298  12-22-87   8:42 am
    SYS$HELP DAT       17343   8-11-87  10:06 am
    CHKVOL   EXE       49407   7-20-89   3:02 pm
    SYS$ERR  DAT        6489   7-29-87   9:57 am
    ALLOW    EXE       20859   8-15-89   2:55 pm
    FLAG     EXE       29837   5-30-90  11:24 am
    REMOVE   EXE       32333   5-31-90  12:21 pm
    SMODE    EXE       27573   6-06-90  12:27 pm
    LOGOUT   EXE       29255   5-31-90   8:16 am
    NDIR     EXE       95374   6-02-90  11:10 am
    LOGIN    EXE       96171   5-29-90   1:52 pm
    NCOPY    EXE       56189   6-22-90  11:19 am
    ATTACH   EXE       36885   5-10-90  11:10 am
    MAP      EXE       47463   4-26-90   3:56 pm
    PURGE    EXE       25983   2-16-90   7:43 am
    RENDIR   EXE       20185   2-02-90  11:05 am
    REVOKE   EXE       34621   2-06-90   2:20 pm
    SEND     EXE       21109   3-01-90   3:25 pm
    SLIST    EXE       25143   5-10-90  11:11 am
    RIGHTS   EXE       18761   4-25-90  10:46 am
    SYSTIME  EXE       16225   4-30-90  12:21 pm
    SETTTS   EXE       16855   5-18-90   8:41 am
    WHOAMI   EXE       25723   5-18-90  11:05 am
    SETPASS  EXE       31935   5-24-90   4:48 pm
    NVER     EXE       13543   1-11-90   2:12 pm
    LISTDIR  EXE       26389   5-29-90   9:29 am
    TLIST    EXE       29799   5-29-90   3:55 pm


DOSUTIL-.1/SYSTEM

  BINDREST EXE       12397   8-04-89  10:47 am
    TOKEN    RPL       12788   6-05-90   4:51 pm
    DOSGEN   EXE        9724   4-12-88  12:41 pm
    NET$REC  DAT         381   4-13-87   8:58 am
    SECURITY EXE       22385   8-03-89   8:33 am
    ATOTAL   EXE       18941   7-28-89  10:57 am
    PAUDIT   EXE       27255   7-18-89  11:41 am
    BINDFIX  EXE       41519   1-19-90  11:08 am


DOSUTIL-.2/PUBLIC

    FCONSOLE HLP      136188   4-06-90   2:52 pm
    FCONSOLE EXE      202774   5-02-90   6:00 pm
    MENUPARZ HLP        1184   2-14-89   3:51 pm
    MAIN     MNU         318   2-03-88   5:04 pm
    COLORPAL EXE       50176  10-20-87   9:33 am
    DSPACE   EXE      196585   8-08-90   2:01 pm
    COLORPAL HLP        3503   5-29-90   1:56 pm
    DSPACE   HLP        5575   5-29-90  10:54 am
    MAKEUSER HLP        1845   5-31-90  11:49 am
    FILER    EXE      271369   6-04-90   3:43 pm
    FILER    HLP       60138   6-04-90  11:03 am
    MENU     EXE       10752  10-04-89   8:58 am
    MENUPARZ EXE       51632  10-04-89   8:59 am
    MAKEUSER EXE      133595   5-14-90  10:46 am


DOSUTIL-.3/PUBLIC

    SESSION  EXE      130839   4-26-90   4:13 pm
    SALVAGE  EXE      129787   5-02-90   7:05 pm
    USERDEF  EXE      173837   4-27-90   2:21 pm
    VOLINFO  EXE      142235   4-26-90   3:39 pm
    SYSCON   EXE      270103   5-29-90   1:23 pm
    SALVAGE  HLP        6788   5-29-90   2:50 pm
    SESSION  HLP       20129   5-29-90   3:11 pm
    VOLINFO  HLP        7442   5-29-90   2:11 pm
    SYSCON   HLP      142570   6-03-90   1:42 pm
    USERDEF  HLP       24718   6-04-90  11:13 am


HELP-1/PUBLIC

    PVMANUAL NFO      114688   6-08-90   3:58 pm
    VIEWER   EXE       75907   5-25-90  12:46 pm
    VIEWS    PTR       17506   4-06-90  11:19 am
    USER-BAS ICS       58096   6-01-90   2:48 pm
    HELP     EXE       14825   6-07-90   9:41 am
    VIEWS    CFG         465   8-07-89   1:22 pm
    CONST    NFO       90112   6-08-90   9:40 pm
    BRDGEXT  PCX        6317   5-18-90   1:37 pm
    BRDGINT  PCX        6329   5-18-90   1:38 pm
    BRIDGBB  PCX       11270   5-18-90   1:38 pm
    CACHMEM1 PCX       10312   5-18-90   1:38 pm
    CACHMEM2 PCX        7460   5-18-90   1:38 pm
    DIRCACHE PCX        6602   5-18-90   1:39 pm
    DSKDULPX PCX        7833   5-18-90   1:39 pm
    ETHERFRM PCX        6053   5-18-90   1:39 pm
    ETHERMUL PCX        8628   5-18-90   1:40 pm
    FOLIO    NFO      110592   6-08-90   9:37 pm
    MOUSE    PCX       47077   6-07-90   9:25 am
    HASHING1 PCX        5960   5-18-90   1:40 pm
    HASHING2 PCX        5336   5-18-90   1:40 pm
    MUSIC    RS        49759   6-08-90  12:00 am
    MESSPACK PCX        8322   5-18-90   1:40 pm
    MIRROR   PCX        5545   5-18-90   1:41 pm
    NETNUM1  PCX        7143   5-18-90   1:41 pm
    NETNUM2  PCX        6870   5-18-90   1:41 pm
    PARTITIO PCX        5310   5-18-90   1:42 pm
    SECUR1   PCX        8829   5-18-90   1:42 pm
    SECUR2   PCX        9049   5-18-90   1:42 pm
    SECUR3   PCX        7557   5-18-90   1:42 pm
    SECUR4   PCX        7407   5-18-90   1:42 pm
    NFOLIO   COM       10500   3-06-90   9:48 am
    RCD      PCX       20031  10-02-89  12:19 pm
    VOICE    RS        54081   6-08-90  12:37 am
    NFOLIO   EXE      185577   5-04-90   9:32 am

HELP-2/PUBLIC

    !NETWARE NFO     1064960   6-08-90   2:47 pm


PRINT/SYSTEM/NLM

    PSERVER  NLM       73641   6-11-90   2:08 pm

PRINT/SYSTEM/VAP

    PSERVER  VAP       63986  12-08-89   9:20 am


PRINT/PUBLIC

    ENDCAP   EXE       13553   7-19-89  10:55 am
    PSC      EXE       20037   7-26-89  10:50 am
    PRINTDEF EXE      180211   5-04-90  11:05 am
    CAPTURE  EXE       41025   5-04-90   9:20 am
    PCONSOLE EXE      213096   5-11-90   3:07 pm
    PRINTCON EXE      152661   5-21-90   9:51 am
    PRINTCON HLP       12261   5-29-90   2:14 pm
    PRINTDEF HLP       36714   5-29-90   2:41 pm
    RPRINTER HLP        1803   5-29-90   2:42 pm
    PCONSOLE HLP       33117   5-31-90  11:10 am
    PSERVER  EXE      108262   6-01-90   9:11 am
    RPRINT$$ EXE       76892   6-01-90   4:14 pm
    NPRINT   EXE       61021   5-21-90   3:32 pm
    RPRINTER EXE        6326   6-11-90  12:49 pm


PRINT/PUBLIC/PDF

    DIAB630  PDF         261   9-21-88   9:58 am
    CIT20    PDF         281   9-21-88   9:57 am
    CITOH600 PDF         380   9-21-88   9:58 am
    PAN1091  PDF         437   9-21-88  10:06 am
    STAR10X  PDF         285   9-21-88  10:07 am
    EPLQ800  PDF         293   9-21-88  10:00 am
    EPLX80   PDF         282   9-21-88  10:01 am
    EPLX800  PDF         284   9-21-88  10:01 am
    HPLASER  PDF        1527   9-21-88  10:01 am
    IBM4201  PDF         368   9-21-88  10:02 am
    IBMPRO2  PDF         369   9-21-88  10:02 am
    NECP6    PDF         538   9-21-88  10:03 am
    OKI390   PDF         282   9-21-88  10:04 am
    STAR1000 PDF         283   9-21-88  10:07 am
    TOSHP321 PDF         400   9-21-88  10:07 am
    CIT224   PDF         356   9-21-88   9:57 am
    APPIMAGE PDF         292   9-21-88   9:56 am
    APPLASER PDF         201   9-21-88   9:56 am
    CIT120D  PDF         284   9-21-88   9:57 am
    EPEX800  PDF         284   9-21-88   9:59 am
    EPLD2500 PDF         285   9-21-88  10:00 am
    OKI290   PDF         281   9-21-88  10:04 am
    NEC8810  PDF         277   9-21-88  10:06 am
    CITOH310 PDF         286   9-21-88   9:58 am
    EPEX86   PDF         290   9-21-88  10:00 am
    NEC2050  PDF         258   9-21-88  10:06 am
    EPEX80   PDF         287   9-21-88   9:59 am
    OKILASER PDF        1516   9-21-88  10:04 am
    OKI192   PDF         298   9-21-88  10:06 am
    PAN1080  PDF         323   9-21-88  10:04 am


SHGEN-1

    IBM$RUN  OVL        2400   7-13-89   9:30 am
    S3C503   OBJ        6313   5-07-90   1:11 pm
    DCONFIG  EXE       22247   6-06-88  11:46 am
    JUMPERS  HLP        1766   4-05-90   4:40 pm
    JUMPERS  EXE       76203   5-07-90   1:38 pm
    SYS$HELP DAT       17343   8-11-87  10:06 am
    SHELLS   DAT          23   8-17-87   1:44 pm
    VOLUMES  DAT          40   2-10-88   9:31 am
    SYS$MSG  DAT       22298  12-22-87   8:42 am
    SYS$ERR  DAT        6489   7-29-87   9:57 am
    INT2F    COM         640   7-28-88  11:48 am
    NLINK    EXE       37633   8-10-89   9:37 am
    CMPQ$RUN OVL        2400   7-26-89  10:26 pm
    ECONFIG  EXE       24269   4-14-88   8:21 am
    COMCHECK EXE       76840   9-01-87  11:53 am
    $RUN     OVL        2400   7-13-89   9:30 am
    SHCONFIG EXE       97365   9-14-89   3:36 pm
    ROUTE    COM        3431   1-18-90  11:56 am
    S3C501   OBJ        4309  10-03-88   1:56 pm
    NETBIOS  EXE       23088   4-20-90   2:25 pm
    STOKEN   OBJ        5333   5-15-90   8:42 am
    SNE1000  OBJ        5415  12-27-89   2:30 pm
    XMSNET4  EXE       56056   6-06-90   4:40 pm
    S3C505   OBJ        8664   8-04-88   8:42 am
    S3C523   OBJ        7069  10-10-88   4:35 pm
    STRXNET  OBJ        6811   6-11-90   1:40 pm
    S3C501   LAN        1131   6-11-90   2:47 pm
    S3C503   LAN         389   6-11-90   2:47 pm
    S3C505   LAN         914   6-11-90   2:47 pm
    S3C523   LAN         110   6-11-90   2:47 pm
    SLANSUP  LAN         113   6-11-90   2:47 pm
    SNE1000  LAN         883   6-11-90   2:47 pm
    SNE2     LAN         135   6-11-90   2:47 pm
    SNE2000  LAN         883   6-11-90   2:47 pm
    STOKEN   LAN         100   6-11-90   2:47 pm
    STRXNET  LAN         479   6-11-90   2:47 pm
    SNE2000  OBJ        6121  12-27-89  12:16 pm
    SNE2     OBJ        4781  11-29-89   1:55 pm
    SHGEN    EXE       26321   5-04-89  10:06 am
    SLANSUP  OBJ        4267   5-24-90   8:21 am
    COMCHECK HLP        2543   5-29-90   2:03 pm
    SHCONFIG HLP       28961   5-29-90   4:01 pm
    IPX      OBJ       19429   6-05-90  11:32 am
    EMSNET3  EXE       58584   6-06-90   4:40 pm
    EMSNET4  EXE       59000   6-06-90   4:39 pm
    NET3     COM       48546   6-06-90   4:39 pm
    NET4     COM       48909   6-06-90   4:38 pm
    XMSNET3  EXE       55672   6-06-90   4:40 pm


SHGEN-1/DOSODI

    3C503    COM       11202   5-30-90  12:00 pm
    3C523    COM       10971   5-30-90  12:00 pm
    IPXODI   COM       19017   5-30-90  12:00 pm
    LANSUP   COM       10784   5-30-90  12:00 pm
    LSL      COM        6399   5-30-90  12:00 pm
    NE1000   COM       11186   5-30-90  12:00 pm
    NE2-32   COM       11138   5-30-90  12:00 pm
    NE2      COM       11465   5-30-90  12:00 pm
    NE2000   COM       11272   5-30-90  12:00 pm


SYSTEM-.1

    SERVER   EXE      716988   6-14-90  10:57 am
    README   386       11734   7-14-90   2:20 pm
    FILES    DAT       43086   7-14-90   2:29 pm
    MAC      NAM       14311   4-24-90   8:56 am
    DISKSET  NLM       69297   6-05-90   2:28 pm
    INSTALL  NLM      139824   6-05-90  11:03 am
    VREPAIR  NLM       86874   6-05-90   4:05 pm
    DISKSET  HLP        6192   6-04-90   2:48 pm
    DCB      DSK       18313   6-11-90   3:47 pm
    ISADISK  DSK        7586   6-11-90   4:17 pm
    PS2ESDI  DSK        6973   6-08-90   5:17 pm
    PS2MFM   DSK        8275   6-08-90   5:23 pm
    PS2SCSI  DSK        9556   6-08-90   5:30 pm


SYSTEM-.2

    REMOTE   NLM        9215   4-13-90   7:42 am
    3C523    LAN       11922   5-08-90   8:23 pm
    ROUTE    NLM        4506   4-27-90   3:20 pm
    RCONSOLE HLP        8402   4-25-90  12:55 pm
    NE2000   LAN       10863   5-17-90  11:41 am
    NE3200   LAN       19710   5-23-90   5:09 pm
    TRXNET   LAN        8682   5-21-90   3:57 pm
    NE2      LAN       10802   5-25-90   6:44 pm
    RCONSOLE EXE       77551   5-26-90   2:35 pm
    3C505    LAN       20541   5-28-90   8:11 pm
    NE2-32   LAN       10810   5-31-90  12:06 pm
    3C503    LAN       11160   6-05-90  11:17 am
    MONITOR  NLM      100391   6-05-90  10:50 am
    TOKENRPL NLM       16454   6-05-90   5:02 pm
    UPS      NLM       10547   6-05-90   2:21 pm
    RSPX     NLM       17064   5-11-90   1:37 pm
    CLIB     NLM      203748   6-08-90   3:31 pm
    IPXS     NLM        3378   6-07-90   6:42 pm
    MATHLIB  NLM       12477   6-08-90   3:32 pm
    NE1000   LAN       10018   6-08-90   9:29 am
    NMAGENT  NLM       33862   6-07-90   3:37 pm
    SPXS     NLM        4538   6-07-90   6:41 pm
    STREAMS  NLM       45504   6-08-90   8:50 am
    TLI      NLM        8795   6-08-90  12:42 pm
    TOKEN    LAN        9544   6-07-90   3:29 pm
    MATHLIBC NLM       16772   6-08-90   3:32 pm
    FILEDATA DAT        1398   6-11-90   9:15 pm


UPGRADE/SYSTEM

    $RUN     OVL        2400   7-13-89   9:30 am
    IBM$RUN  OVL        2400   7-13-89   9:30 am
    DIBI$DRV DAT          30   6-29-89   8:53 pm
    SYS$MSG  DAT       22298  12-22-87   8:42 am
    SYS$HELP DAT       17343   8-11-87  10:06 am
    SYS$ERR  DAT        6489   7-29-87   9:57 am
    CMPQ$RUN OVL        2400   7-26-89  10:26 pm
    SELDIBI  HLP         229   6-24-89   3:45 pm
    UPGRADE  HLP       41447   5-31-90  10:46 am
    UPGRADE  EXE      246860   4-13-90  11:48 am
    UPGRADE  OVL      245514   4-13-90  11:49 am
    SELDIBI  OVL       54250  12-08-89   3:18 pm
    UPGRADE  COM       10262  12-08-89   3:17 pm
    WANGTEK  EXE       22950  12-08-89   3:19 pm